Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3dd767b104c066996f38aefeb63832f202a7c9df0a2baa70b0271af42569c315

Tx prefix hash: 6488cd4662629d3b9039b5b6e6ee2779623907bfa57aa0d81a12cfd016b3d464
Tx public key: d14cc96a3a32265bd8c481341c060d087e695851a397423da44d262dc36a45d9
Timestamp: 1736562260 Timestamp [UCT]: 2025-01-11 02:24:20 Age [y:d:h:m:s]: 00:067:21:01:15
Block: 1194716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48316 RingCT/type: yes/0
Extra: 01d14cc96a3a32265bd8c481341c060d087e695851a397423da44d262dc36a45d9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6d80d2a7b0687e1113a1d494c2042398afb4a3dbb3e6ea181e124a81580af66 0.600000000000 1681293 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": 1194726, "vin": [ { "gen": { "height": 1194716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6d80d2a7b0687e1113a1d494c2042398afb4a3dbb3e6ea181e124a81580af66" } } ], "extra": [ 1, 209, 76, 201, 106, 58, 50, 38, 91, 216, 196, 129, 52, 28, 6, 13, 8, 126, 105, 88, 81, 163, 151, 66, 61, 164, 77, 38, 45, 195, 106, 69, 217, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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