Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65bce50793c66ccbdfc2d62648c813423f3b7b0826984a0bdfd59d0f2205ac0d

Tx prefix hash: 07873edd56a28142fbf817757d08df49c7c80ea4d0bcb0791a7e1593f3a97fb9
Tx public key: 774c5606406686cae0393921e732bf7e41f87ec09429c5255334fb4f34a4f667
Timestamp: 1703308307 Timestamp [UCT]: 2023-12-23 05:11:47 Age [y:d:h:m:s]: 01:025:07:44:02
Block: 919173 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279428 RingCT/type: yes/0
Extra: 01774c5606406686cae0393921e732bf7e41f87ec09429c5255334fb4f34a4f6670211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 13a835559d48af00c5cf2206faa3a6aa4e4fb242ea037b92408eff2b9a0f1e85 0.600000000000 1376837 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": 919183, "vin": [ { "gen": { "height": 919173 } } ], "vout": [ { "amount": 600000000, "target": { "key": "13a835559d48af00c5cf2206faa3a6aa4e4fb242ea037b92408eff2b9a0f1e85" } } ], "extra": [ 1, 119, 76, 86, 6, 64, 102, 134, 202, 224, 57, 57, 33, 231, 50, 191, 126, 65, 248, 126, 192, 148, 41, 197, 37, 83, 52, 251, 79, 52, 164, 246, 103, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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