Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60bc024a5270d967b2a242ca79391574e04a61111e4bc815694b168a9f3ac0e2

Tx prefix hash: ec97e15e631faf7eaaf94dd8e1f3a999eac439518fda005b8a90f33dd60ef144
Tx public key: f894577d8d34af844397346de73f694f86b47ad621b57bc6a1fe319bb4fb2fff
Timestamp: 1728302768 Timestamp [UCT]: 2024-10-07 12:06:08 Age [y:d:h:m:s]: 00:208:02:47:48
Block: 1126393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148541 RingCT/type: yes/0
Extra: 01f894577d8d34af844397346de73f694f86b47ad621b57bc6a1fe319bb4fb2fff02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dfe5fdeedf7d1e7b20529b75d2ec0effd27fc0084b3758014a2d30dd2dfbe9e 0.600000000000 1609184 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": 1126403, "vin": [ { "gen": { "height": 1126393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dfe5fdeedf7d1e7b20529b75d2ec0effd27fc0084b3758014a2d30dd2dfbe9e" } } ], "extra": [ 1, 248, 148, 87, 125, 141, 52, 175, 132, 67, 151, 52, 109, 231, 63, 105, 79, 134, 180, 122, 214, 33, 181, 123, 198, 161, 254, 49, 155, 180, 251, 47, 255, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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