Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 18394f41945bcff890c56d438030669b84bb4071e8bd77011ec9d06b81f8045a

Tx prefix hash: 7aa07c5205adbfb2b9ac7c002f01c45b6605a5f28801f01570db497bc9dc06a1
Tx public key: 41bde8b41f14a7fdb0747843e3e88bb46c1f0f988c3e8a1825632d95bc8e5f3f
Timestamp: 1713302916 Timestamp [UCT]: 2024-04-16 21:28:36 Age [y:d:h:m:s]: 01:027:11:57:12
Block: 1002016 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280635 RingCT/type: yes/0
Extra: 0141bde8b41f14a7fdb0747843e3e88bb46c1f0f988c3e8a1825632d95bc8e5f3f0211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a6e8490b0d72b18ad0be22552fd6131e3069a07e6898c4bbfbc17b2e84a2ac6 0.600000000000 1462530 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": 1002026, "vin": [ { "gen": { "height": 1002016 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a6e8490b0d72b18ad0be22552fd6131e3069a07e6898c4bbfbc17b2e84a2ac6" } } ], "extra": [ 1, 65, 189, 232, 180, 31, 20, 167, 253, 176, 116, 120, 67, 227, 232, 139, 180, 108, 31, 15, 152, 140, 62, 138, 24, 37, 99, 45, 149, 188, 142, 95, 63, 2, 17, 0, 0, 0, 6, 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