Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 695123dd055d6a32e409a8e7a2a1b70da620173b6525ea34f479678eea6ead91

Tx prefix hash: 1edb9e82453737d5d421ee3a459bad4c03c8537b756fc294bd588acaac993800
Tx public key: 9c2ca6f4cfc6ee6ca7022e4e10f958462ada1d3e4733f6e6449aa22aaf9e1858
Timestamp: 1704993327 Timestamp [UCT]: 2024-01-11 17:15:27 Age [y:d:h:m:s]: 01:304:14:21:38
Block: 933133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 476514 RingCT/type: yes/0
Extra: 019c2ca6f4cfc6ee6ca7022e4e10f958462ada1d3e4733f6e6449aa22aaf9e185802110000000c59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 168dfe224c3925db43ceef5aa88ac0a2a4498adaa399011e2549852548fbe263 0.600000000000 1391089 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": 933143, "vin": [ { "gen": { "height": 933133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "168dfe224c3925db43ceef5aa88ac0a2a4498adaa399011e2549852548fbe263" } } ], "extra": [ 1, 156, 44, 166, 244, 207, 198, 238, 108, 167, 2, 46, 78, 16, 249, 88, 70, 42, 218, 29, 62, 71, 51, 246, 230, 68, 154, 162, 42, 175, 158, 24, 88, 2, 17, 0, 0, 0, 12, 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