Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64c1d8c84b35d51fc0896d5fc22b3e9db24ab85732b72b679e430fe1426c9808

Tx prefix hash: ba17de1657984a1e488267c9bd710af0b98c1f62b8e0d935b56aef562d1daf8b
Tx public key: 86b3a990060c7eaf3aba99e4249ba61a2a40f31d45b1adf77e82ad86f3c6c4d0
Timestamp: 1697233435 Timestamp [UCT]: 2023-10-13 21:43:55 Age [y:d:h:m:s]: 02:027:14:31:11
Block: 869008 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 539349 RingCT/type: yes/0
Extra: 0186b3a990060c7eaf3aba99e4249ba61a2a40f31d45b1adf77e82ad86f3c6c4d0021100000007e6d27f9c000000000000000000

1 output(s) for total of 0.810243923000 dcy

stealth address amount amount idx
00: 872cba76bafb3a81118d129cb2a7c7faaabdf1d2c9bbed6e00cfd56bde09a371 0.810243923000 1323835 of 0

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": 869018, "vin": [ { "gen": { "height": 869008 } } ], "vout": [ { "amount": 810243923, "target": { "key": "872cba76bafb3a81118d129cb2a7c7faaabdf1d2c9bbed6e00cfd56bde09a371" } } ], "extra": [ 1, 134, 179, 169, 144, 6, 12, 126, 175, 58, 186, 153, 228, 36, 155, 166, 26, 42, 64, 243, 29, 69, 177, 173, 247, 126, 130, 173, 134, 243, 198, 196, 208, 2, 17, 0, 0, 0, 7, 230, 210, 127, 156, 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