Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1299fc29966910e72432d277e1facf2a4b33123d595b8dc2feff1ee9c3fe8e46

Tx prefix hash: e67ec80a0a1f57ca3715de7c8990cce794bfcb4a113864f20906f9a53bad60f5
Tx public key: b082f815f94d5e29abc65ef0dce80b20af80e35df1598e554e21222ca6e6d8a5
Timestamp: 1718613124 Timestamp [UCT]: 2024-06-17 08:32:04 Age [y:d:h:m:s]: 00:286:17:02:08
Block: 1046060 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204869 RingCT/type: yes/0
Extra: 01b082f815f94d5e29abc65ef0dce80b20af80e35df1598e554e21222ca6e6d8a502110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 923c5743ead3f4c9f4e0ed6e9aea07d4eb38196af87c7d4b72455b71b0d06dc9 0.600000000000 1515811 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": 1046070, "vin": [ { "gen": { "height": 1046060 } } ], "vout": [ { "amount": 600000000, "target": { "key": "923c5743ead3f4c9f4e0ed6e9aea07d4eb38196af87c7d4b72455b71b0d06dc9" } } ], "extra": [ 1, 176, 130, 248, 21, 249, 77, 94, 41, 171, 198, 94, 240, 220, 232, 11, 32, 175, 128, 227, 93, 241, 89, 142, 85, 78, 33, 34, 44, 166, 230, 216, 165, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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