Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7bbec80788108c591d2bc13db3dd4700fb1be24f151d274f476c62acfd8c631

Tx prefix hash: a822a6711bc6044bd84fae3f9a1b7ca7b80414b0fefb538c886e8815e4f51323
Tx public key: 0326579cbdd5292097e21eae0d84f570d0c33dcf37f56d5fecaeda2c137d3199
Timestamp: 1709166808 Timestamp [UCT]: 2024-02-29 00:33:28 Age [y:d:h:m:s]: 01:102:08:49:48
Block: 967746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334229 RingCT/type: yes/0
Extra: 010326579cbdd5292097e21eae0d84f570d0c33dcf37f56d5fecaeda2c137d319902110000000d0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2ef0128910e0a4a71481fafabfcf4af88ee3ab46a754c5fc343a77556eb35b4 0.600000000000 1427531 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": 967756, "vin": [ { "gen": { "height": 967746 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2ef0128910e0a4a71481fafabfcf4af88ee3ab46a754c5fc343a77556eb35b4" } } ], "extra": [ 1, 3, 38, 87, 156, 189, 213, 41, 32, 151, 226, 30, 174, 13, 132, 245, 112, 208, 195, 61, 207, 55, 245, 109, 95, 236, 174, 218, 44, 19, 125, 49, 153, 2, 17, 0, 0, 0, 13, 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