Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54540d3f8ce80d1a161d842ee4daa166765d3fa98fe6d85630c65ec1aee0fdc3

Tx prefix hash: cfef73a2c9c7bb5322ffb2184a5126b689b174f746fbce4e3deec6f93dc03505
Tx public key: 35e8093c6581dd16a15913c0c10aefec9aa706107e0fb68952716033de4cd771
Timestamp: 1723482455 Timestamp [UCT]: 2024-08-12 17:07:35 Age [y:d:h:m:s]: 00:234:15:16:07
Block: 1086428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167573 RingCT/type: yes/0
Extra: 0135e8093c6581dd16a15913c0c10aefec9aa706107e0fb68952716033de4cd77102110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2e33cbeefc7a1da85f93eaa0c5ba6fde84f928e21fc3b3cd1933d2a35d317561 0.600000000000 1561025 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": 1086438, "vin": [ { "gen": { "height": 1086428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2e33cbeefc7a1da85f93eaa0c5ba6fde84f928e21fc3b3cd1933d2a35d317561" } } ], "extra": [ 1, 53, 232, 9, 60, 101, 129, 221, 22, 161, 89, 19, 192, 193, 10, 239, 236, 154, 167, 6, 16, 126, 15, 182, 137, 82, 113, 96, 51, 222, 76, 215, 113, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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