Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6b9a23252150bbf309ee7a75ba1da9be8154d0128a84baa35435165f37761e7

Tx prefix hash: aac8a0f51898248f29f02084056ed5aa7601992a7cc8443f4516c84ed8f0ae29
Tx public key: 37bfcec6c0f55cc2e9f08eea55c6749eb5edb74291263de862b93e06d8f7c3d2
Timestamp: 1717239985 Timestamp [UCT]: 2024-06-01 11:06:25 Age [y:d:h:m:s]: 00:312:00:49:59
Block: 1034680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 223008 RingCT/type: yes/0
Extra: 0137bfcec6c0f55cc2e9f08eea55c6749eb5edb74291263de862b93e06d8f7c3d202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 069712519103e8f090c9b722a8b83a5c9d22e1ea539ce5e912eb7158b4a07159 0.600000000000 1503197 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": 1034690, "vin": [ { "gen": { "height": 1034680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "069712519103e8f090c9b722a8b83a5c9d22e1ea539ce5e912eb7158b4a07159" } } ], "extra": [ 1, 55, 191, 206, 198, 192, 245, 92, 194, 233, 240, 142, 234, 85, 198, 116, 158, 181, 237, 183, 66, 145, 38, 61, 232, 98, 185, 62, 6, 216, 247, 195, 210, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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