Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efcbec4adcd67f38f0121facddf80c7feddf5a5c2282d63c1ce7f940a60784e8

Tx prefix hash: 2ea9d409455aece7b33bc4d5e3eaeceb267c0dff3ca253a7b6dffaacf7c4272a
Tx public key: b4cbfdd16e95f89e5daecb555a762053754e5021e825772051b63a317607b299
Timestamp: 1578788705 Timestamp [UCT]: 2020-01-12 00:25:05 Age [y:d:h:m:s]: 05:294:19:08:31
Block: 43540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1358599 RingCT/type: yes/0
Extra: 01b4cbfdd16e95f89e5daecb555a762053754e5021e825772051b63a317607b2990211000000234943cd9f000000000000000000

1 output(s) for total of 440.285870172000 dcy

stealth address amount amount idx
00: 3108693d28bda518e99243a58fc69ed7a9a3a6e1fefd3791e5baadac73af4332 440.285870172000 78905 of 0

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": 43550, "vin": [ { "gen": { "height": 43540 } } ], "vout": [ { "amount": 440285870172, "target": { "key": "3108693d28bda518e99243a58fc69ed7a9a3a6e1fefd3791e5baadac73af4332" } } ], "extra": [ 1, 180, 203, 253, 209, 110, 149, 248, 158, 93, 174, 203, 85, 90, 118, 32, 83, 117, 78, 80, 33, 232, 37, 119, 32, 81, 182, 58, 49, 118, 7, 178, 153, 2, 17, 0, 0, 0, 35, 73, 67, 205, 159, 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