Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce10a3d2be22da6633f4d5a611a1495400b9e59c79c1e274cdb93d4c6982309

Tx prefix hash: 953e84d297fd35871a194b50c36860cd52ecdb9daa3eae67eeb80a9bd7d5a4d4
Tx public key: 8cbda926cda59e55f8680cc9ddcca1bbaa1ae1a61825cb1b8892451e1b9e746a
Timestamp: 1638902447 Timestamp [UCT]: 2021-12-07 18:40:47 Age [y:d:h:m:s]: 03:156:02:27:01
Block: 390549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 890299 RingCT/type: yes/0
Extra: 018cbda926cda59e55f8680cc9ddcca1bbaa1ae1a61825cb1b8892451e1b9e746a02110000002ce9564d6f000000000000000000

1 output(s) for total of 31.187022473000 dcy

stealth address amount amount idx
00: bf6cd76fa2361b246605afab993f9e13786b096c4ac6d31a546fda53c1084c1b 31.187022473000 786368 of 0

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": 390559, "vin": [ { "gen": { "height": 390549 } } ], "vout": [ { "amount": 31187022473, "target": { "key": "bf6cd76fa2361b246605afab993f9e13786b096c4ac6d31a546fda53c1084c1b" } } ], "extra": [ 1, 140, 189, 169, 38, 205, 165, 158, 85, 248, 104, 12, 201, 221, 204, 161, 187, 170, 26, 225, 166, 24, 37, 203, 27, 136, 146, 69, 30, 27, 158, 116, 106, 2, 17, 0, 0, 0, 44, 233, 86, 77, 111, 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