Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13cd5a2f3377283b6b946d58a8ecd86f7a7011f20260a99544d472d06eed1114

Tx prefix hash: 8e16eca2d02d4af2c08453d59f7613fa79c6d624787b768b02ce8bfc72de59dc
Tx public key: 030d3e5d2f513b0a4f7128453af194d40ebb48bca4b156d6e83b659dcbadd841
Timestamp: 1686894756 Timestamp [UCT]: 2023-06-16 05:52:36 Age [y:d:h:m:s]: 01:218:06:24:20
Block: 783345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417359 RingCT/type: yes/0
Extra: 01030d3e5d2f513b0a4f7128453af194d40ebb48bca4b156d6e83b659dcbadd84102110000000233af99f4000000000000000000

1 output(s) for total of 1.557589416000 dcy

stealth address amount amount idx
00: 03a24375db2f220fbce28733acf40a77a6dd56d11a6aec40bd5d148d5f017bdf 1.557589416000 1233200 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": 783355, "vin": [ { "gen": { "height": 783345 } } ], "vout": [ { "amount": 1557589416, "target": { "key": "03a24375db2f220fbce28733acf40a77a6dd56d11a6aec40bd5d148d5f017bdf" } } ], "extra": [ 1, 3, 13, 62, 93, 47, 81, 59, 10, 79, 113, 40, 69, 58, 241, 148, 212, 14, 187, 72, 188, 164, 177, 86, 214, 232, 59, 101, 157, 203, 173, 216, 65, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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