Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 594cf69f8f53fc95076e1e2aeb3bf7856772fa56af7423a8e019be6b9282728c

Tx prefix hash: aa0a096711f11fb4d97cb14af6a8c13ab48019a407a5da4ee7c381f09a7ce6a7
Tx public key: 346b09b71bae5babbf0941aaa5ada8a2f9d2f89e68585a4c71cbf231c0c23ebb
Timestamp: 1737185651 Timestamp [UCT]: 2025-01-18 07:34:11 Age [y:d:h:m:s]: 00:153:09:58:06
Block: 1199884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109312 RingCT/type: yes/0
Extra: 01346b09b71bae5babbf0941aaa5ada8a2f9d2f89e68585a4c71cbf231c0c23ebb0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d40db73482f0d1f5f128ead9452585563a0713d37616ec24380a6cfc6cc7943 0.600000000000 1686521 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": 1199894, "vin": [ { "gen": { "height": 1199884 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d40db73482f0d1f5f128ead9452585563a0713d37616ec24380a6cfc6cc7943" } } ], "extra": [ 1, 52, 107, 9, 183, 27, 174, 91, 171, 191, 9, 65, 170, 165, 173, 168, 162, 249, 210, 248, 158, 104, 88, 90, 76, 113, 203, 242, 49, 192, 194, 62, 187, 2, 17, 0, 0, 0, 3, 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