Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df28de5e8a26e4e9b95ed9143bb89b6c92a8b93563015098317a685f61d611d4

Tx prefix hash: b1d489a1fa4959d8505977b9cee5d0262fd81e3b585626025af85428f65e5ef0
Tx public key: dede39fef81f8d9e8dafb3f3d14c70dc31e6e0d81b49e68f379235568fe7a37f
Timestamp: 1670692417 Timestamp [UCT]: 2022-12-10 17:13:37 Age [y:d:h:m:s]: 02:117:03:22:32
Block: 649666 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 605413 RingCT/type: yes/0
Extra: 01dede39fef81f8d9e8dafb3f3d14c70dc31e6e0d81b49e68f379235568fe7a37f021100000001faf35c9c000000000000000000

1 output(s) for total of 4.319036158000 dcy

stealth address amount amount idx
00: 79c6eb502aa0503d9edeab52af57e9a0b1fb78a895a6be87c68f83674fb1a9e3 4.319036158000 1090033 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": 649676, "vin": [ { "gen": { "height": 649666 } } ], "vout": [ { "amount": 4319036158, "target": { "key": "79c6eb502aa0503d9edeab52af57e9a0b1fb78a895a6be87c68f83674fb1a9e3" } } ], "extra": [ 1, 222, 222, 57, 254, 248, 31, 141, 158, 141, 175, 179, 243, 209, 76, 112, 220, 49, 230, 224, 216, 27, 73, 230, 143, 55, 146, 53, 86, 143, 231, 163, 127, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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