Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb6922ac68876938bf9324283b5f4918b2f4948d9ae04dad152d95745dd7c0fa

Tx prefix hash: b3e9323c8b837a7f121e86978fdda425dd13d0f02d65236495959fee62f951b3
Tx public key: b18fb90d254b69bbd33e7d0c2d752fbb9db50930264ae034a3793267d339df70
Timestamp: 1724148361 Timestamp [UCT]: 2024-08-20 10:06:01 Age [y:d:h:m:s]: 01:080:08:52:59
Block: 1091959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315885 RingCT/type: yes/0
Extra: 01b18fb90d254b69bbd33e7d0c2d752fbb9db50930264ae034a3793267d339df70021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72a9091df1f529117e462c08d9c1f00b6683552bdfceda73e9ac8cfda9e0df16 0.600000000000 1566606 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": 1091969, "vin": [ { "gen": { "height": 1091959 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72a9091df1f529117e462c08d9c1f00b6683552bdfceda73e9ac8cfda9e0df16" } } ], "extra": [ 1, 177, 143, 185, 13, 37, 75, 105, 187, 211, 62, 125, 12, 45, 117, 47, 187, 157, 181, 9, 48, 38, 74, 224, 52, 163, 121, 50, 103, 211, 57, 223, 112, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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