Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca3d2587eb12b1b7f3a711a010634584647f82c8f86bfe6974939f750ef640e1

Tx prefix hash: e596a8c873beb5d5756fe38047834386a1baf6a891f54df892de120d74da11df
Tx public key: f480f083d2e13d0395b35d0e375dc4586b9ef80815b6c0b4e82154420e859cc3
Timestamp: 1736429051 Timestamp [UCT]: 2025-01-09 13:24:11 Age [y:d:h:m:s]: 00:155:15:07:07
Block: 1193628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110972 RingCT/type: yes/0
Extra: 01f480f083d2e13d0395b35d0e375dc4586b9ef80815b6c0b4e82154420e859cc30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4fc453bcb511e90ad4d43d101e888d062ae1ba35c0b22b1bc6d5839f85d98f0e 0.600000000000 1680191 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": 1193638, "vin": [ { "gen": { "height": 1193628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4fc453bcb511e90ad4d43d101e888d062ae1ba35c0b22b1bc6d5839f85d98f0e" } } ], "extra": [ 1, 244, 128, 240, 131, 210, 225, 61, 3, 149, 179, 93, 14, 55, 93, 196, 88, 107, 158, 248, 8, 21, 182, 192, 180, 232, 33, 84, 66, 14, 133, 156, 195, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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