Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87804eb180e35d8e0bf8ae0a2072889bcf0adc6c714b519cc4915e7d4b9d3698

Tx prefix hash: 619695cc35c3d3c44aef9ff1df6970249e71d0a82d0f5cab9cc12ddda1921d1e
Tx public key: 5b9b95705cb676d818cd56e567efdd148536d9760fa179915e363e6235bfa7eb
Timestamp: 1699216721 Timestamp [UCT]: 2023-11-05 20:38:41 Age [y:d:h:m:s]: 01:171:04:53:41
Block: 885245 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383575 RingCT/type: yes/0
Extra: 015b9b95705cb676d818cd56e567efdd148536d9760fa179915e363e6235bfa7eb021100000001faf35c9c000000000000000000

1 output(s) for total of 0.715839794000 dcy

stealth address amount amount idx
00: a2e134f3a6e4388e4d7d996640e01b8835197edc6547ab6231a1cbbf2929b10d 0.715839794000 1341008 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": 885255, "vin": [ { "gen": { "height": 885245 } } ], "vout": [ { "amount": 715839794, "target": { "key": "a2e134f3a6e4388e4d7d996640e01b8835197edc6547ab6231a1cbbf2929b10d" } } ], "extra": [ 1, 91, 155, 149, 112, 92, 182, 118, 216, 24, 205, 86, 229, 103, 239, 221, 20, 133, 54, 217, 118, 15, 161, 121, 145, 94, 54, 62, 98, 53, 191, 167, 235, 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