Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab3699f44da50ad491eb0f54219bf26eea6e68d82ecc5b0bc4c7323089bec6c7

Tx prefix hash: 4541ae5233f3dbbeaa236b25b06025b9f511cf7fdeec7647e4957500a61ab71c
Tx public key: e549d71c1d190698c231f76b76fa27b31fdc85b44be5d1c9359d34a4cf12fd4b
Timestamp: 1730526198 Timestamp [UCT]: 2024-11-02 05:43:18 Age [y:d:h:m:s]: 00:152:12:59:40
Block: 1144735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108848 RingCT/type: yes/0
Extra: 01e549d71c1d190698c231f76b76fa27b31fdc85b44be5d1c9359d34a4cf12fd4b0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7e4cedd2863ac52ad16cd20b8680c650475a64128dd3c0f7df2169686727a05 0.600000000000 1629026 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": 1144745, "vin": [ { "gen": { "height": 1144735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7e4cedd2863ac52ad16cd20b8680c650475a64128dd3c0f7df2169686727a05" } } ], "extra": [ 1, 229, 73, 215, 28, 29, 25, 6, 152, 194, 49, 247, 107, 118, 250, 39, 179, 31, 220, 133, 180, 75, 229, 209, 201, 53, 157, 52, 164, 207, 18, 253, 75, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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