Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 589d28d8f2c49ce66becbb9a2219ca31f77e5825f493626fa1190070c451892c

Tx prefix hash: 625919568931f6c4335095e80ec66e587ce9a30c2efd89f5786f58e742e55162
Tx public key: 3b48a075a4f0fc83d2496c68530973ec403a94f2b7a0118c3862d42115c497af
Timestamp: 1700414688 Timestamp [UCT]: 2023-11-19 17:24:48 Age [y:d:h:m:s]: 01:162:20:41:40
Block: 895185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377584 RingCT/type: yes/0
Extra: 013b48a075a4f0fc83d2496c68530973ec403a94f2b7a0118c3862d42115c497af021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.663560425000 dcy

stealth address amount amount idx
00: 9a48492c65b34401eb7b9e7b5c0f90e8e195c1c9a963218272a4e1452fb4c397 0.663560425000 1351408 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": 895195, "vin": [ { "gen": { "height": 895185 } } ], "vout": [ { "amount": 663560425, "target": { "key": "9a48492c65b34401eb7b9e7b5c0f90e8e195c1c9a963218272a4e1452fb4c397" } } ], "extra": [ 1, 59, 72, 160, 117, 164, 240, 252, 131, 210, 73, 108, 104, 83, 9, 115, 236, 64, 58, 148, 242, 183, 160, 17, 140, 56, 98, 212, 33, 21, 196, 151, 175, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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