Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acf7798966120535641e29df9fb54f3830e7ffcf733d197bae99f1f5be1d256d

Tx prefix hash: 9384f3e5c9a65d8d387b0cdd8af9008c034eba85ba6d188bc2489482b8d1efb4
Tx public key: b6a7cb02a25f852ed2e60197f48c37d2fe524e8755729f2fca56db28295bffec
Timestamp: 1736552214 Timestamp [UCT]: 2025-01-10 23:36:54 Age [y:d:h:m:s]: 00:025:11:16:05
Block: 1194631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17963 RingCT/type: yes/0
Extra: 01b6a7cb02a25f852ed2e60197f48c37d2fe524e8755729f2fca56db28295bffec021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04804378a725dc22a84655213d1ea375f421d121ab2b833a6e31cdc78ab08841 0.600000000000 1681208 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": 1194641, "vin": [ { "gen": { "height": 1194631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04804378a725dc22a84655213d1ea375f421d121ab2b833a6e31cdc78ab08841" } } ], "extra": [ 1, 182, 167, 203, 2, 162, 95, 133, 46, 210, 230, 1, 151, 244, 140, 55, 210, 254, 82, 78, 135, 85, 114, 159, 47, 202, 86, 219, 40, 41, 91, 255, 236, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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