Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 923f886bda676fba81dc224ecfbbc5c98ed0bbe55dfe285b209bf417069ef1cb

Tx prefix hash: 52fdb87e434fc383da3a769ab878d36a3ba7b3ca8ecf8f12a44442e5a8892dff
Tx public key: 7181bd3377da95294f6147d368b9c057dce11a6f5a0f03e18d36bb3ec74c7a3e
Timestamp: 1733888668 Timestamp [UCT]: 2024-12-11 03:44:28 Age [y:d:h:m:s]: 00:108:02:16:53
Block: 1172609 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77032 RingCT/type: yes/0
Extra: 017181bd3377da95294f6147d368b9c057dce11a6f5a0f03e18d36bb3ec74c7a3e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c74f9db25ec817c7e38c3599223bbacea6fe3dcb768f67a35124ab8398afb22b 0.600000000000 1658524 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": 1172619, "vin": [ { "gen": { "height": 1172609 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c74f9db25ec817c7e38c3599223bbacea6fe3dcb768f67a35124ab8398afb22b" } } ], "extra": [ 1, 113, 129, 189, 51, 119, 218, 149, 41, 79, 97, 71, 211, 104, 185, 192, 87, 220, 225, 26, 111, 90, 15, 3, 225, 141, 54, 187, 62, 199, 76, 122, 62, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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