Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb44def88468c0809486e2f1d0f9a38369fc074ca39e0dcc8c487a1d053a3f66

Tx prefix hash: 17dc48b04829086f4c4dc79ed7081578d6bb57ad03c211a325bb6c0de1abbe7c
Tx public key: b3254cfca4704fe513e8ab40a114b37f7758fb5a14fa6a98306da83863717321
Timestamp: 1705594060 Timestamp [UCT]: 2024-01-18 16:07:40 Age [y:d:h:m:s]: 00:314:22:30:49
Block: 938106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225518 RingCT/type: yes/0
Extra: 01b3254cfca4704fe513e8ab40a114b37f7758fb5a14fa6a98306da838637173210211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8bfae44420fefe6ab2d45454319e69669345ff6547f1b881c7c4a4a031dc9a4 0.600000000000 1396172 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": 938116, "vin": [ { "gen": { "height": 938106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8bfae44420fefe6ab2d45454319e69669345ff6547f1b881c7c4a4a031dc9a4" } } ], "extra": [ 1, 179, 37, 76, 252, 164, 112, 79, 229, 19, 232, 171, 64, 161, 20, 179, 127, 119, 88, 251, 90, 20, 250, 106, 152, 48, 109, 168, 56, 99, 113, 115, 33, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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