Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ab56a66e35f8dffe4ab266e39905a48c6f8fe839585bfb4ee9aa24584de6611

Tx prefix hash: 989bfe0873ffa88734ad9b04ae58f94a9c875661c43f4125f4d55eca3b042cff
Tx public key: 21bdbabfea9ca86f3dfdc209977a7c6a38cd8a0c3538f64f0765e8d5de0cff2e
Timestamp: 1715337179 Timestamp [UCT]: 2024-05-10 10:32:59 Age [y:d:h:m:s]: 00:353:05:41:38
Block: 1018900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252511 RingCT/type: yes/0
Extra: 0121bdbabfea9ca86f3dfdc209977a7c6a38cd8a0c3538f64f0765e8d5de0cff2e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f7b12573eeaaa573ef4f7f39269a9d09a6aa6b0728c6fb2c7be68ca94d72fc7 0.600000000000 1482715 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": 1018910, "vin": [ { "gen": { "height": 1018900 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f7b12573eeaaa573ef4f7f39269a9d09a6aa6b0728c6fb2c7be68ca94d72fc7" } } ], "extra": [ 1, 33, 189, 186, 191, 234, 156, 168, 111, 61, 253, 194, 9, 151, 122, 124, 106, 56, 205, 138, 12, 53, 56, 246, 79, 7, 101, 232, 213, 222, 12, 255, 46, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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