Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c16fbf023bc46828bbbd1fa545b4c650b401ec39fdcab92336507e89a854a64f

Tx prefix hash: fa5c5bf5f9e74a1b3a0f38add8b11a683b2701e4163404a6326013d3d8a528e9
Tx public key: 87dedf321c2c86a00689cbddac1a19419b88db9a1a1681bc80c63aed08d2bd3e
Timestamp: 1705692523 Timestamp [UCT]: 2024-01-19 19:28:43 Age [y:d:h:m:s]: 01:150:03:01:42
Block: 938906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368331 RingCT/type: yes/0
Extra: 0187dedf321c2c86a00689cbddac1a19419b88db9a1a1681bc80c63aed08d2bd3e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 905d3d453ccf6e02560d7e4778af4307d03a0f9430a093f00dec4ce7448ff082 0.600000000000 1396988 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": 938916, "vin": [ { "gen": { "height": 938906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "905d3d453ccf6e02560d7e4778af4307d03a0f9430a093f00dec4ce7448ff082" } } ], "extra": [ 1, 135, 222, 223, 50, 28, 44, 134, 160, 6, 137, 203, 221, 172, 26, 25, 65, 155, 136, 219, 154, 26, 22, 129, 188, 128, 198, 58, 237, 8, 210, 189, 62, 2, 17, 0, 0, 0, 3, 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