Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f3519ebcae4b131c48cfc23dba2c282dc140f1238fbda65e95b77cf4e30f7ee

Tx prefix hash: aed5a1d662c27b9c1e5d879b8201e66806d46a18bddfd96e8d277be1669c38b7
Tx public key: 33f8fa1e235aa5809bcf3d0dd4d1ce1f86c39b4f130110ed1c0158e5c5dc03d1
Timestamp: 1697202944 Timestamp [UCT]: 2023-10-13 13:15:44 Age [y:d:h:m:s]: 01:102:06:09:13
Block: 868755 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 334299 RingCT/type: yes/0
Extra: 0133f8fa1e235aa5809bcf3d0dd4d1ce1f86c39b4f130110ed1c0158e5c5dc03d102110000000533af99f4000000000000000000

1 output(s) for total of 0.811809402000 dcy

stealth address amount amount idx
00: 069d920da90180d0f8c2e7c786c4f6733aa345678a47c8d8cac8281d27ce8644 0.811809402000 1323574 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": 868765, "vin": [ { "gen": { "height": 868755 } } ], "vout": [ { "amount": 811809402, "target": { "key": "069d920da90180d0f8c2e7c786c4f6733aa345678a47c8d8cac8281d27ce8644" } } ], "extra": [ 1, 51, 248, 250, 30, 35, 90, 165, 128, 155, 207, 61, 13, 212, 209, 206, 31, 134, 195, 155, 79, 19, 1, 16, 237, 28, 1, 88, 229, 197, 220, 3, 209, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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