Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e27b013db7ec1bc7f8819784dc6e49179c2e0547e494f88914fb8c74aca801d

Tx prefix hash: 08538e3141edeea5eb9057f12b72e15e71eb69af2deacc29dd4a062a3adf4dd0
Tx public key: ac2f3ae2951988850c17b5818f6d6d47f48fed5c74a8f97d4224601661eb31ab
Timestamp: 1740904273 Timestamp [UCT]: 2025-03-02 08:31:13 Age [y:d:h:m:s]: 00:262:05:37:20
Block: 1230401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 185170 RingCT/type: yes/0
Extra: 01ac2f3ae2951988850c17b5818f6d6d47f48fed5c74a8f97d4224601661eb31ab021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7f0a7029ed3a90251e3d6019c5f1139b693fc5ebf539f3a2d6f822e2f35e1eb 0.600000000000 1717298 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": 1230411, "vin": [ { "gen": { "height": 1230401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7f0a7029ed3a90251e3d6019c5f1139b693fc5ebf539f3a2d6f822e2f35e1eb" } } ], "extra": [ 1, 172, 47, 58, 226, 149, 25, 136, 133, 12, 23, 181, 129, 143, 109, 109, 71, 244, 143, 237, 92, 116, 168, 249, 125, 66, 36, 96, 22, 97, 235, 49, 171, 2, 17, 0, 0, 0, 2, 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