Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5be50513eab68bcacfd75db637396819c261e32c43885b67c2eb70d39ff03e2

Tx prefix hash: 72c390596490e6edc5844c52420fb3e9b1de5f998d694efec1bde2681f14a8b6
Tx public key: 6b2d4ae70a2351ffea8950b5d0c658e7ff0d3889db95c23549d76513cbf03070
Timestamp: 1747186190 Timestamp [UCT]: 2025-05-14 01:29:50 Age [y:d:h:m:s]: 00:191:19:50:28
Block: 1282416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134801 RingCT/type: yes/0
Extra: 016b2d4ae70a2351ffea8950b5d0c658e7ff0d3889db95c23549d76513cbf030700211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea3007c87161b2ac0266a6f4f6b86c09c62b46bac8bddfc8e48b5f69bc5e5a27 0.600000000000 1769823 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": 1282426, "vin": [ { "gen": { "height": 1282416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea3007c87161b2ac0266a6f4f6b86c09c62b46bac8bddfc8e48b5f69bc5e5a27" } } ], "extra": [ 1, 107, 45, 74, 231, 10, 35, 81, 255, 234, 137, 80, 181, 208, 198, 88, 231, 255, 13, 56, 137, 219, 149, 194, 53, 73, 215, 101, 19, 203, 240, 48, 112, 2, 17, 0, 0, 0, 3, 31, 144, 81, 122, 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