Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f31024521179c1a8ad80a3bef8b1375bd38a97cd2238d32e83f0b958e398ba3

Tx prefix hash: e993543e2d60a930c8d6534d8f74e607a5edbca4a0e2fed6840994f78bec5a05
Tx public key: 740c8fadb30bd2a3e6dbb30bf9145c882172c32722e8af159d279b87c4d49a14
Timestamp: 1734031313 Timestamp [UCT]: 2024-12-12 19:21:53 Age [y:d:h:m:s]: 00:330:00:03:24
Block: 1173798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233341 RingCT/type: yes/0
Extra: 01740c8fadb30bd2a3e6dbb30bf9145c882172c32722e8af159d279b87c4d49a140211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b5467412fcdef25f8f1ab3baed2ec2b8d8ba00f738fcf8079fdfa20218d933c5 0.600000000000 1659863 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": 1173808, "vin": [ { "gen": { "height": 1173798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b5467412fcdef25f8f1ab3baed2ec2b8d8ba00f738fcf8079fdfa20218d933c5" } } ], "extra": [ 1, 116, 12, 143, 173, 179, 11, 210, 163, 230, 219, 179, 11, 249, 20, 92, 136, 33, 114, 195, 39, 34, 232, 175, 21, 157, 39, 155, 135, 196, 212, 154, 20, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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