Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 880b4355651527dde1f58a85e312821714bb0e4d1cedeeb2c895a7e5012cc3f3

Tx prefix hash: e1f48c99e635884c050fc8dd703b804d58d0ca4791bea47084dcc4969912dab2
Tx public key: cab97620e25a712fa3e14e27e835fb6741c8a0ba0032e3e068413a56047d2cd9
Timestamp: 1708683985 Timestamp [UCT]: 2024-02-23 10:26:25 Age [y:d:h:m:s]: 01:044:08:42:07
Block: 963742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 292715 RingCT/type: yes/0
Extra: 01cab97620e25a712fa3e14e27e835fb6741c8a0ba0032e3e068413a56047d2cd902110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5696dbe4d46f9f55677fedf183df041afb63e9a8d8d148812435c562fb314215 0.600000000000 1423467 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": 963752, "vin": [ { "gen": { "height": 963742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5696dbe4d46f9f55677fedf183df041afb63e9a8d8d148812435c562fb314215" } } ], "extra": [ 1, 202, 185, 118, 32, 226, 90, 113, 47, 163, 225, 78, 39, 232, 53, 251, 103, 65, 200, 160, 186, 0, 50, 227, 224, 104, 65, 58, 86, 4, 125, 44, 217, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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