Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b9114d037db443c9bc39e468deee78c713d91669ab9f2825aae9757b9598ca2

Tx prefix hash: e0d85d2db3c55448f32dfdaac2d71d66fae2fd13c20d9b2b1861820d7070b1ba
Tx public key: c281fe754515746e5a431f134f01ad407d0e372823d45e7a7665d8f5f020c138
Timestamp: 1704385449 Timestamp [UCT]: 2024-01-04 16:24:09 Age [y:d:h:m:s]: 01:014:18:46:31
Block: 928108 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 271880 RingCT/type: yes/0
Extra: 01c281fe754515746e5a431f134f01ad407d0e372823d45e7a7665d8f5f020c138021100000009679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a8ad3a55018297d0d0f585b4360414e8faffe031d78add89eaa36557aac2ab36 0.600000000000 1385964 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": 928118, "vin": [ { "gen": { "height": 928108 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a8ad3a55018297d0d0f585b4360414e8faffe031d78add89eaa36557aac2ab36" } } ], "extra": [ 1, 194, 129, 254, 117, 69, 21, 116, 110, 90, 67, 31, 19, 79, 1, 173, 64, 125, 14, 55, 40, 35, 212, 94, 122, 118, 101, 216, 245, 240, 32, 193, 56, 2, 17, 0, 0, 0, 9, 103, 154, 138, 129, 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