Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b783e0da299f90ca7b13e83eeeb4861e9eb825f5d84e58fbf3549e577a915df4

Tx prefix hash: 09eff1a7f8d0fe903807d06a41041928ff26c0a9189ed33cdf46c131c391f5c8
Tx public key: af1f9d13ef73f34a42a07724a64a8096c7ac414c0b582534afe923a02ded04f7
Timestamp: 1724983913 Timestamp [UCT]: 2024-08-30 02:11:53 Age [y:d:h:m:s]: 00:215:16:02:40
Block: 1098868 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 153996 RingCT/type: yes/0
Extra: 01af1f9d13ef73f34a42a07724a64a8096c7ac414c0b582534afe923a02ded04f702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a84b771cc1c87cfe3ef6d504b2a55896f49a5d99bf13667292529471a83ba5ae 0.600000000000 1574731 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": 1098878, "vin": [ { "gen": { "height": 1098868 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a84b771cc1c87cfe3ef6d504b2a55896f49a5d99bf13667292529471a83ba5ae" } } ], "extra": [ 1, 175, 31, 157, 19, 239, 115, 243, 74, 66, 160, 119, 36, 166, 74, 128, 150, 199, 172, 65, 76, 11, 88, 37, 52, 175, 233, 35, 160, 45, 237, 4, 247, 2, 17, 0, 0, 0, 7, 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