Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e6c2675816072370216530dbc6049110ce9b8f0ca5f3aa85b51416a614b4735

Tx prefix hash: 3c130ea3394ab2d053f6a49a37fddd281882552c6ccbe95dcd2e277852de3801
Tx public key: ca3b19a39574f9c2e405e49831d4c8cdd05a2a54dbfda22afd7924fc15c723a3
Timestamp: 1719103675 Timestamp [UCT]: 2024-06-23 00:47:55 Age [y:d:h:m:s]: 00:285:01:41:43
Block: 1050107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 203709 RingCT/type: yes/0
Extra: 01ca3b19a39574f9c2e405e49831d4c8cdd05a2a54dbfda22afd7924fc15c723a302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03f60634f2fcceeb4aa87ece15740c480a95b20eaf170e3369b010785c2dc7c1 0.600000000000 1520264 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": 1050117, "vin": [ { "gen": { "height": 1050107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03f60634f2fcceeb4aa87ece15740c480a95b20eaf170e3369b010785c2dc7c1" } } ], "extra": [ 1, 202, 59, 25, 163, 149, 116, 249, 194, 228, 5, 228, 152, 49, 212, 200, 205, 208, 90, 42, 84, 219, 253, 162, 42, 253, 121, 36, 252, 21, 199, 35, 163, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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