Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e79eaf874b5a5b420b81a45883eef87cdc40721e57b2a2258a12a8c14e7af4d

Tx prefix hash: b8df6b19f3995756e5f2b7bcbe99a2a479c3b7fd55816d467a494c2c99f47fbf
Tx public key: 70790a1e289cf1f05b799a22e9b88953ba0b76605cfb5ca7b29c94f12564568b
Timestamp: 1736021130 Timestamp [UCT]: 2025-01-04 20:05:30 Age [y:d:h:m:s]: 00:304:19:59:51
Block: 1190248 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215350 RingCT/type: yes/0
Extra: 0170790a1e289cf1f05b799a22e9b88953ba0b76605cfb5ca7b29c94f12564568b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d27333fea3a5e38d82391b0bbb7ca3aec56fbfa64f57eddaabf3cbc174df2ba2 0.600000000000 1676763 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": 1190258, "vin": [ { "gen": { "height": 1190248 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d27333fea3a5e38d82391b0bbb7ca3aec56fbfa64f57eddaabf3cbc174df2ba2" } } ], "extra": [ 1, 112, 121, 10, 30, 40, 156, 241, 240, 91, 121, 154, 34, 233, 184, 137, 83, 186, 11, 118, 96, 92, 251, 92, 167, 178, 156, 148, 241, 37, 100, 86, 139, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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