Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8db5289093fd15f682189569895b8b99c0607e4bcf1579afb8ebea7b6230dc7d

Tx prefix hash: 1fa6da5348f190a37b9a7ec1c6f176699b00d6e7dcfdb212a6ca6f1dedd376a6
Tx public key: 3e3ec9a1a4932950709bc2760393da09ff9701c4c501bc87bd5d2f13745a2ed5
Timestamp: 1720837184 Timestamp [UCT]: 2024-07-13 02:19:44 Age [y:d:h:m:s]: 00:256:05:23:35
Block: 1064509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183023 RingCT/type: yes/0
Extra: 013e3ec9a1a4932950709bc2760393da09ff9701c4c501bc87bd5d2f13745a2ed5021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b189b2d5f67df7dfc7c44fb08ce9f5ee593379e630d28bbec4ede77031c838d4 0.600000000000 1535038 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": 1064519, "vin": [ { "gen": { "height": 1064509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b189b2d5f67df7dfc7c44fb08ce9f5ee593379e630d28bbec4ede77031c838d4" } } ], "extra": [ 1, 62, 62, 201, 161, 164, 147, 41, 80, 112, 155, 194, 118, 3, 147, 218, 9, 255, 151, 1, 196, 197, 1, 188, 135, 189, 93, 47, 19, 116, 90, 46, 213, 2, 17, 0, 0, 0, 2, 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