Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93e034ccef628e9d7225fbb44711b43ec2ebfb16e4c5fb65ecf94c71f1390174

Tx prefix hash: 0e075e219d6babb0051b6fd683a1c1f5e9b9f189ba83f3776c0d5ade594c30f8
Tx public key: 581652ad169255b8dabb916d9e5feac4647f03565a6874bc3bae998d57d6ef20
Timestamp: 1686063591 Timestamp [UCT]: 2023-06-06 14:59:51 Age [y:d:h:m:s]: 02:012:06:20:18
Block: 776453 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 530745 RingCT/type: yes/0
Extra: 01581652ad169255b8dabb916d9e5feac4647f03565a6874bc3bae998d57d6ef2002110000000275e3f0e9000000000000000000

1 output(s) for total of 1.641772068000 dcy

stealth address amount amount idx
00: 6915b934f9ccb813932389234c5e9b78539ba83573b8d67e7d7121f5f9d61cd2 1.641772068000 1226006 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": 776463, "vin": [ { "gen": { "height": 776453 } } ], "vout": [ { "amount": 1641772068, "target": { "key": "6915b934f9ccb813932389234c5e9b78539ba83573b8d67e7d7121f5f9d61cd2" } } ], "extra": [ 1, 88, 22, 82, 173, 22, 146, 85, 184, 218, 187, 145, 109, 158, 95, 234, 196, 100, 127, 3, 86, 90, 104, 116, 188, 59, 174, 153, 141, 87, 214, 239, 32, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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