Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a15579303cb707da15c54f037d9e30949c29eb221b427fe3ed74d282cc45f4b

Tx prefix hash: 46795d2ad3d595df58d0c856c4e0a95c567bff96d91de043b0910f9cc1cacd4e
Tx public key: 1c6b0c8210c3347f16cd1f6d6487bc9f8d54373da838ce9a76a4870d0eab799d
Timestamp: 1577860857 Timestamp [UCT]: 2020-01-01 06:40:57 Age [y:d:h:m:s]: 05:064:05:00:31
Block: 36184 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1195748 RingCT/type: yes/0
Extra: 011c6b0c8210c3347f16cd1f6d6487bc9f8d54373da838ce9a76a4870d0eab799d0211000000494ac5aa02000000000000000000

1 output(s) for total of 465.702147419000 dcy

stealth address amount amount idx
00: 8d8da871550fdf4c7c7577cfc4dd21e4488aac5d0c5b6a7a4b5bd12055bfd4e9 465.702147419000 61220 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": 36194, "vin": [ { "gen": { "height": 36184 } } ], "vout": [ { "amount": 465702147419, "target": { "key": "8d8da871550fdf4c7c7577cfc4dd21e4488aac5d0c5b6a7a4b5bd12055bfd4e9" } } ], "extra": [ 1, 28, 107, 12, 130, 16, 195, 52, 127, 22, 205, 31, 109, 100, 135, 188, 159, 141, 84, 55, 61, 168, 56, 206, 154, 118, 164, 135, 13, 14, 171, 121, 157, 2, 17, 0, 0, 0, 73, 74, 197, 170, 2, 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