Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 03cb04ce9b3672b57b5f099c57cf2e330727ac35568d3316e4035d33fe65f685

Tx prefix hash: f93b2ba71c4534041e39fd7a88f54f4d899d6f67a9f18c9eba3271f47a5db324
Tx public key: a43fd2bf5dfcd7bbf7ab05dba53d823a111559cd8f2547f23e1e9b767520fbb0
Timestamp: 1717604633 Timestamp [UCT]: 2024-06-05 16:23:53 Age [y:d:h:m:s]: 01:168:02:52:01
Block: 1037699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378739 RingCT/type: yes/0
Extra: 01a43fd2bf5dfcd7bbf7ab05dba53d823a111559cd8f2547f23e1e9b767520fbb002110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d99f674dd854d500f24ce4373b00768f2dc20031da8ce76962a74f2b3ec1dcf4 0.600000000000 1506252 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": 1037709, "vin": [ { "gen": { "height": 1037699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d99f674dd854d500f24ce4373b00768f2dc20031da8ce76962a74f2b3ec1dcf4" } } ], "extra": [ 1, 164, 63, 210, 191, 93, 252, 215, 187, 247, 171, 5, 219, 165, 61, 130, 58, 17, 21, 89, 205, 143, 37, 71, 242, 62, 30, 155, 118, 117, 32, 251, 176, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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