Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e8f25f62c8cf82a337afaa1a113dd84c5fce110130e2791d88d1277c1e48e7c

Tx prefix hash: 007c42ded71fd596d2a9eb0a414bd54375bb8fb3d2ef10382596457aabea0a56
Tx public key: 41716a3db9c23ab481114c1e26c316d7f818cb314ddce8d2234ba44195a933ef
Timestamp: 1726843122 Timestamp [UCT]: 2024-09-20 14:38:42 Age [y:d:h:m:s]: 00:222:01:56:28
Block: 1114292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158545 RingCT/type: yes/0
Extra: 0141716a3db9c23ab481114c1e26c316d7f818cb314ddce8d2234ba44195a933ef0211000000032c3a34dc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 05a23054334dbe343a6315a74f67fd5cce165041a1f1bb0e4735efdddd869bc4 0.600000000000 1594091 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": 1114302, "vin": [ { "gen": { "height": 1114292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "05a23054334dbe343a6315a74f67fd5cce165041a1f1bb0e4735efdddd869bc4" } } ], "extra": [ 1, 65, 113, 106, 61, 185, 194, 58, 180, 129, 17, 76, 30, 38, 195, 22, 215, 248, 24, 203, 49, 77, 220, 232, 210, 35, 75, 164, 65, 149, 169, 51, 239, 2, 17, 0, 0, 0, 3, 44, 58, 52, 220, 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