Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 78d487b29197f289b7a37c59c709198cbd7f67c2a6032fe7827ac550f858bccc

Tx prefix hash: 516fa593b14457236825de2d98819190de9f9d9554bc8af8c493c8bd4eec74ff
Tx public key: c06707406c6d1c5ed7c18dd93a3b29b44a0b61535ae5a486d0947c3a5b819b87
Timestamp: 1725302119 Timestamp [UCT]: 2024-09-02 18:35:19 Age [y:d:h:m:s]: 00:211:19:16:31
Block: 1101511 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151226 RingCT/type: yes/0
Extra: 01c06707406c6d1c5ed7c18dd93a3b29b44a0b61535ae5a486d0947c3a5b819b87021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2463f20eeecb5f75bd540b4eccd9456269d709ce66528f0461a0908b485c5ef2 0.600000000000 1577590 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": 1101521, "vin": [ { "gen": { "height": 1101511 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2463f20eeecb5f75bd540b4eccd9456269d709ce66528f0461a0908b485c5ef2" } } ], "extra": [ 1, 192, 103, 7, 64, 108, 109, 28, 94, 215, 193, 141, 217, 58, 59, 41, 180, 74, 11, 97, 83, 90, 229, 164, 134, 208, 148, 124, 58, 91, 129, 155, 135, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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