Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda8ce412cdf2249232fae6f16b98e96a3ef885d4c3015540ae5611772b3fbf7

Tx prefix hash: 17a647ed1a9a547a5a7917f6df15f2bb991e897caecc9d661c2afb33530913dc
Tx public key: e84bb74479870eab7c5bd14d76e984749a9bf8b23f06bacc437e04d2beaf6cf0
Timestamp: 1686999356 Timestamp [UCT]: 2023-06-17 10:55:56 Age [y:d:h:m:s]: 01:269:11:29:24
Block: 784216 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453767 RingCT/type: yes/0
Extra: 01e84bb74479870eab7c5bd14d76e984749a9bf8b23f06bacc437e04d2beaf6cf0021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.547273194000 dcy

stealth address amount amount idx
00: 34bc85f56e10daad8b20e0a8676f86a5e22e3056e4dfdba908950c948512bf4b 1.547273194000 1234101 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": 784226, "vin": [ { "gen": { "height": 784216 } } ], "vout": [ { "amount": 1547273194, "target": { "key": "34bc85f56e10daad8b20e0a8676f86a5e22e3056e4dfdba908950c948512bf4b" } } ], "extra": [ 1, 232, 75, 183, 68, 121, 135, 14, 171, 124, 91, 209, 77, 118, 233, 132, 116, 154, 155, 248, 178, 63, 6, 186, 204, 67, 126, 4, 210, 190, 175, 108, 240, 2, 17, 0, 0, 0, 2, 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