Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e73622dca013cd67f6c17ce6ce6c69660a2989bde64972da38ad8afede8cba4

Tx prefix hash: 3ffd60f3372c540f47bd8bf7a9ca297e88540c0e115fb395807128fa3b774b4f
Tx public key: e2bfc0f38877b4f089c91ab7f92974d0b44d242d3e4462ee35a79262d65b5da6
Timestamp: 1731927455 Timestamp [UCT]: 2024-11-18 10:57:35 Age [y:d:h:m:s]: 00:005:20:01:42
Block: 1156349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4169 RingCT/type: yes/0
Extra: 01e2bfc0f38877b4f089c91ab7f92974d0b44d242d3e4462ee35a79262d65b5da6021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 652b26a1f93b44c38b66c559c88e4a43de70db979c91cf71bffc268bbf8fa6d4 0.600000000000 1641972 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": 1156359, "vin": [ { "gen": { "height": 1156349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "652b26a1f93b44c38b66c559c88e4a43de70db979c91cf71bffc268bbf8fa6d4" } } ], "extra": [ 1, 226, 191, 192, 243, 136, 119, 180, 240, 137, 201, 26, 183, 249, 41, 116, 208, 180, 77, 36, 45, 62, 68, 98, 238, 53, 167, 146, 98, 214, 91, 93, 166, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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