Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd03e747cda190c1f28d6362b5da53cbdbd06fa0f98808394bd059cb31f4189d

Tx prefix hash: 8e0c439dccb3ba10a2f5496c1571546edb36161473c32d99c88c4e39b9e57381
Tx public key: ce3e0e340e2988d2c7acefb9c440630b66d18dc233f27e9bac9232dd19729819
Timestamp: 1578864613 Timestamp [UCT]: 2020-01-12 21:30:13 Age [y:d:h:m:s]: 05:124:12:06:11
Block: 44204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1239162 RingCT/type: yes/0
Extra: 01ce3e0e340e2988d2c7acefb9c440630b66d18dc233f27e9bac9232dd197298190211000000224ac5aa02000000000000000000

1 output(s) for total of 438.061049721000 dcy

stealth address amount amount idx
00: 2dfb42636edd3eba709e0be1a3ad529e7963e00effba65efbdf3a84062ec763f 438.061049721000 80364 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": 44214, "vin": [ { "gen": { "height": 44204 } } ], "vout": [ { "amount": 438061049721, "target": { "key": "2dfb42636edd3eba709e0be1a3ad529e7963e00effba65efbdf3a84062ec763f" } } ], "extra": [ 1, 206, 62, 14, 52, 14, 41, 136, 210, 199, 172, 239, 185, 196, 64, 99, 11, 102, 209, 141, 194, 51, 242, 126, 155, 172, 146, 50, 221, 25, 114, 152, 25, 2, 17, 0, 0, 0, 34, 74, 197, 170, 2, 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