Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 15d4a7fabdf4d7337ce266d767ba49a806ce1d2bbfce25e2d65267892fd023fb

Tx prefix hash: 0908d902cfc27a23933d29025236805b7f6c5cdcb6222e95d274952c464993e5
Tx public key: bc3ec3fdb58b718976196253e0ed9a4cd521a716b91721f059684699589b672c
Timestamp: 1581965193 Timestamp [UCT]: 2020-02-17 18:46:33 Age [y:d:h:m:s]: 04:314:17:22:19
Block: 66999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1117276 RingCT/type: yes/0
Extra: 01bc3ec3fdb58b718976196253e0ed9a4cd521a716b91721f059684699589b672c02110000000a4943cd9f000000000000000000

1 output(s) for total of 368.146203384000 dcy

stealth address amount amount idx
00: 4f8edd2454fd26084ec8905d59eee58c30c5c0fa155973f82386e1a69619db15 368.146203384000 123376 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": 67009, "vin": [ { "gen": { "height": 66999 } } ], "vout": [ { "amount": 368146203384, "target": { "key": "4f8edd2454fd26084ec8905d59eee58c30c5c0fa155973f82386e1a69619db15" } } ], "extra": [ 1, 188, 62, 195, 253, 181, 139, 113, 137, 118, 25, 98, 83, 224, 237, 154, 76, 213, 33, 167, 22, 185, 23, 33, 240, 89, 104, 70, 153, 88, 155, 103, 44, 2, 17, 0, 0, 0, 10, 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