Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8489686e0e0989f366ba76b7e1e82628f0330d0afdac2d76c4fd02ab13f3221a

Tx prefix hash: da2df550af7adec6d418401ce7a2384c5bda60b8ea59c4e3a10c2cb68c190484
Tx public key: af529fde21099b58d4262f447cbb0c02b0ba30e63ca0765b0a004856915b151a
Timestamp: 1715151108 Timestamp [UCT]: 2024-05-08 06:51:48 Age [y:d:h:m:s]: 01:186:00:40:09
Block: 1017362 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391572 RingCT/type: yes/0
Extra: 01af529fde21099b58d4262f447cbb0c02b0ba30e63ca0765b0a004856915b151a02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 30e70932e1f178fdc2ef7f9646f39fa5180cb8f3ef61a2222c8ee14aeecff144 0.600000000000 1481137 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": 1017372, "vin": [ { "gen": { "height": 1017362 } } ], "vout": [ { "amount": 600000000, "target": { "key": "30e70932e1f178fdc2ef7f9646f39fa5180cb8f3ef61a2222c8ee14aeecff144" } } ], "extra": [ 1, 175, 82, 159, 222, 33, 9, 155, 88, 212, 38, 47, 68, 124, 187, 12, 2, 176, 186, 48, 230, 60, 160, 118, 91, 10, 0, 72, 86, 145, 91, 21, 26, 2, 17, 0, 0, 0, 4, 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