Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab3dd84b132af912cb492e14e9fde89b23ddc1d964da608f0c555e48a7a154b3

Tx prefix hash: 3c45faac230a372dc1c95c48320c92cd69ab188ced7ff9dc9b9678ba7b7cc89f
Tx public key: 8b44b29af2a5c5ee3294fa816e84b099b6a43fdae3bcbfb32d71a16d49d8c90d
Timestamp: 1723880895 Timestamp [UCT]: 2024-08-17 07:48:15 Age [y:d:h:m:s]: 00:227:19:19:30
Block: 1089738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162661 RingCT/type: yes/0
Extra: 018b44b29af2a5c5ee3294fa816e84b099b6a43fdae3bcbfb32d71a16d49d8c90d021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0191a4c713fa6f53826cc5d2bf4a5d632ecbde3697c71b273f3af803ea3d2f1 0.600000000000 1564361 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": 1089748, "vin": [ { "gen": { "height": 1089738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0191a4c713fa6f53826cc5d2bf4a5d632ecbde3697c71b273f3af803ea3d2f1" } } ], "extra": [ 1, 139, 68, 178, 154, 242, 165, 197, 238, 50, 148, 250, 129, 110, 132, 176, 153, 182, 164, 63, 218, 227, 188, 191, 179, 45, 113, 161, 109, 73, 216, 201, 13, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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