Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 437bf2f2aabfb0cf4cf535ca95a49cfd2ed330d3ff8ece35e0dcd1cabc4795be

Tx prefix hash: 4c65564afc2e4590d9ebe9eef6dc2e688271a050affba9fae025db2e06a72937
Tx public key: c4b714381703a711cca90cf8e8a63be02bbec1a3676b6b136668e11df8fd8716
Timestamp: 1626595896 Timestamp [UCT]: 2021-07-18 08:11:36 Age [y:d:h:m:s]: 03:217:14:20:14
Block: 296115 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 926817 RingCT/type: yes/0
Extra: 01c4b714381703a711cca90cf8e8a63be02bbec1a3676b6b136668e11df8fd87160211000000caed79a617000000000000000000

1 output(s) for total of 64.100825012000 dcy

stealth address amount amount idx
00: 36915586420dc28c88df4cdfa3a667bf8c6021123d186818bf6d31c70a2129ba 64.100825012000 619961 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": 296125, "vin": [ { "gen": { "height": 296115 } } ], "vout": [ { "amount": 64100825012, "target": { "key": "36915586420dc28c88df4cdfa3a667bf8c6021123d186818bf6d31c70a2129ba" } } ], "extra": [ 1, 196, 183, 20, 56, 23, 3, 167, 17, 204, 169, 12, 248, 232, 166, 59, 224, 43, 190, 193, 163, 103, 107, 107, 19, 102, 104, 225, 29, 248, 253, 135, 22, 2, 17, 0, 0, 0, 202, 237, 121, 166, 23, 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