Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d095b418bccda0b699326afe30a9dab647a8c465bd70cd59b6bc5b3ea83b467

Tx prefix hash: c24e70700b35cc26f4e6ed8341854fd0fee8734ba0750abdc33ffdb9d4d737d9
Tx public key: 4de0f940872bf7441c3417c8e818be9c8a6c7910bd46a39b1b53997f2a4231a8
Timestamp: 1717050547 Timestamp [UCT]: 2024-05-30 06:29:07 Age [y:d:h:m:s]: 01:019:05:48:00
Block: 1033110 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 274543 RingCT/type: yes/0
Extra: 014de0f940872bf7441c3417c8e818be9c8a6c7910bd46a39b1b53997f2a4231a80211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 66e0263bfb5daae292873b8a7ae9b35d6df009e1332345cf6910bd87991f658f 0.600000000000 1501571 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": 1033120, "vin": [ { "gen": { "height": 1033110 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66e0263bfb5daae292873b8a7ae9b35d6df009e1332345cf6910bd87991f658f" } } ], "extra": [ 1, 77, 224, 249, 64, 135, 43, 247, 68, 28, 52, 23, 200, 232, 24, 190, 156, 138, 108, 121, 16, 189, 70, 163, 155, 27, 83, 153, 127, 42, 66, 49, 168, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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