Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd19e9fcf4171b3f13f420cdf3edd83075e73cea6dc115a129de4fb9a9d61b23

Tx prefix hash: e39be6e812e150e8c00174de0cbecffd29513ab95a4e4387a7943e08e88a2f3f
Tx public key: 4cad45c1ef09da1633fc5ce9c33022092a66f1e43179a821e3b09935e2897f83
Timestamp: 1698471347 Timestamp [UCT]: 2023-10-28 05:35:47 Age [y:d:h:m:s]: 02:010:00:06:19
Block: 879289 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 526712 RingCT/type: yes/0
Extra: 014cad45c1ef09da1633fc5ce9c33022092a66f1e43179a821e3b09935e2897f83021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.749118542000 dcy

stealth address amount amount idx
00: f5cadde63cc487ad9f35b11219e43397093f9178cef197036ad22e2c1cbf4d75 0.749118542000 1334799 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": 879299, "vin": [ { "gen": { "height": 879289 } } ], "vout": [ { "amount": 749118542, "target": { "key": "f5cadde63cc487ad9f35b11219e43397093f9178cef197036ad22e2c1cbf4d75" } } ], "extra": [ 1, 76, 173, 69, 193, 239, 9, 218, 22, 51, 252, 92, 233, 195, 48, 34, 9, 42, 102, 241, 228, 49, 121, 168, 33, 227, 176, 153, 53, 226, 137, 127, 131, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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