Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb99952b35829f84887e498e7df1f713947f215d41501b5689c6697a91fb680

Tx prefix hash: 4ced644726bf681c88f92d53f873a0e3ac8b1531ff2e3edcc76c17356d0e8053
Tx public key: 84f8b941d7ac3a306a0e1abe1a0f90ba6c0ec9d5417330bf50941952b627d250
Timestamp: 1705770783 Timestamp [UCT]: 2024-01-20 17:13:03 Age [y:d:h:m:s]: 01:087:00:21:42
Block: 939557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323300 RingCT/type: yes/0
Extra: 0184f8b941d7ac3a306a0e1abe1a0f90ba6c0ec9d5417330bf50941952b627d2500211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6eb58414b084914f4c1764da01ae877aaa755e21b64ff9d42cbfa22e4f829e0b 0.600000000000 1397665 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": 939567, "vin": [ { "gen": { "height": 939557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6eb58414b084914f4c1764da01ae877aaa755e21b64ff9d42cbfa22e4f829e0b" } } ], "extra": [ 1, 132, 248, 185, 65, 215, 172, 58, 48, 106, 14, 26, 190, 26, 15, 144, 186, 108, 14, 201, 213, 65, 115, 48, 191, 80, 148, 25, 82, 182, 39, 210, 80, 2, 17, 0, 0, 0, 3, 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