Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357238a8e15e5c051a06eff13605715b83195eaf31c2d6b865fdcf47bd5e0fc7

Tx prefix hash: bdbd18b78fe17effc6486d78ff6ac71f6095a85c6b03e3b755677cc8638cdecf
Tx public key: d1398b80a35c6d5150e64a0fabd283246b1d1a19eaf354cc24e59fd31ddc6bb1
Timestamp: 1740339972 Timestamp [UCT]: 2025-02-23 19:46:12 Age [y:d:h:m:s]: 00:226:11:48:38
Block: 1225713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159587 RingCT/type: yes/0
Extra: 01d1398b80a35c6d5150e64a0fabd283246b1d1a19eaf354cc24e59fd31ddc6bb1021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6011171998410a5035c113fb09b2ce85053c5af3b0a20a7803d5c6295785c76b 0.600000000000 1712580 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": 1225723, "vin": [ { "gen": { "height": 1225713 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6011171998410a5035c113fb09b2ce85053c5af3b0a20a7803d5c6295785c76b" } } ], "extra": [ 1, 209, 57, 139, 128, 163, 92, 109, 81, 80, 230, 74, 15, 171, 210, 131, 36, 107, 29, 26, 25, 234, 243, 84, 204, 36, 229, 159, 211, 29, 220, 107, 177, 2, 17, 0, 0, 0, 3, 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