Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: f33ef3f240057414c1e2360b9e70f2dfa5566f8f18339195475c8669ce2377bb

Tx prefix hash: 47dcf91ea57eb43ee7f99557798ff07ff65907cb423d93cf75ce80b932a4c0ac
Tx public key: 52a2408e42a3ad618f7f3f85b18f8259cf5c9ddc2bcf26b5a7c617a60c159a37
Timestamp: 1730831609 Timestamp [UCT]: 2024-11-05 18:33:29 Age [y:d:h:m:s]: 00:053:23:05:17
Block: 1147260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38614 RingCT/type: yes/0
Extra: 0152a2408e42a3ad618f7f3f85b18f8259cf5c9ddc2bcf26b5a7c617a60c159a37021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b14d706497240837aef7438e28dcb82b9c6c15629372ead3738ddda510aa310 0.600000000000 1631955 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1147270, "vin": [ { "gen": { "height": 1147260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b14d706497240837aef7438e28dcb82b9c6c15629372ead3738ddda510aa310" } } ], "extra": [ 1, 82, 162, 64, 142, 66, 163, 173, 97, 143, 127, 63, 133, 177, 143, 130, 89, 207, 92, 157, 220, 43, 207, 38, 181, 167, 198, 23, 166, 12, 21, 154, 55, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8