Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864c99d685e2868cefe6a5ec1f6fade4202cec6fe032d765bf3ba3247248adca

Tx prefix hash: 00f32593429b1566d1d23367f621b79a89bc3b9e35fa7b6a01e2fbe5847a69cb
Tx public key: cc934c5c8a4031a7d6217831d70fb5bcd0418517e2cc101e88a633b907bb712c
Timestamp: 1724105583 Timestamp [UCT]: 2024-08-19 22:13:03 Age [y:d:h:m:s]: 00:297:06:59:54
Block: 1091596 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212326 RingCT/type: yes/0
Extra: 01cc934c5c8a4031a7d6217831d70fb5bcd0418517e2cc101e88a633b907bb712c02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2bbcec355702a0bad0bbb0833ea6ff3f84bf7f0ca0426ba083e932ce3542cba 0.600000000000 1566229 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": 1091606, "vin": [ { "gen": { "height": 1091596 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2bbcec355702a0bad0bbb0833ea6ff3f84bf7f0ca0426ba083e932ce3542cba" } } ], "extra": [ 1, 204, 147, 76, 92, 138, 64, 49, 167, 214, 33, 120, 49, 215, 15, 181, 188, 208, 65, 133, 23, 226, 204, 16, 30, 136, 166, 51, 185, 7, 187, 113, 44, 2, 17, 0, 0, 0, 4, 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