Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd39659e0f4467473b3d515e2bf582c8e5de1522567f30049253ad4b9190c7c8

Tx prefix hash: 00773b4b1dcc43becf939731ca3bd6aacf8473bb8e684c66e8aa5ad03faf2420
Tx public key: 2873eddf9ae27e29a2430a82168cc2696246f0282c780f0c6839a56bc341a17a
Timestamp: 1740112513 Timestamp [UCT]: 2025-02-21 04:35:13 Age [y:d:h:m:s]: 00:229:18:09:00
Block: 1223824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161925 RingCT/type: yes/0
Extra: 012873eddf9ae27e29a2430a82168cc2696246f0282c780f0c6839a56bc341a17a0211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e902aa8181f023c80dd55a787b60dc099246b5bb8b4772d5b9646ce7e9cb8a0 0.600000000000 1710681 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": 1223834, "vin": [ { "gen": { "height": 1223824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e902aa8181f023c80dd55a787b60dc099246b5bb8b4772d5b9646ce7e9cb8a0" } } ], "extra": [ 1, 40, 115, 237, 223, 154, 226, 126, 41, 162, 67, 10, 130, 22, 140, 194, 105, 98, 70, 240, 40, 44, 120, 15, 12, 104, 57, 165, 107, 195, 65, 161, 122, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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