Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3faa3f9b71b4c115f61942b2d60cde296e008f5e5b40761a31e896d846b886e

Tx prefix hash: 536a1e62f13d0973f88ed950c35322e50264d2ec0eff2f203387dc442b7b0fec
Tx public key: 1757fc5ff35b4562de8a196ad1a576415a3db3de80b00f2fc0e8827dd0960051
Timestamp: 1688674195 Timestamp [UCT]: 2023-07-06 20:09:55 Age [y:d:h:m:s]: 01:196:22:14:30
Block: 798109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 402064 RingCT/type: yes/0
Extra: 011757fc5ff35b4562de8a196ad1a576415a3db3de80b00f2fc0e8827dd096005102110000000133af99f4000000000000000000

1 output(s) for total of 1.391661795000 dcy

stealth address amount amount idx
00: a1c77cd01c9951f42de8b9600e0e4c2f37df21484544c7f2d493a021a49f4074 1.391661795000 1249036 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": 798119, "vin": [ { "gen": { "height": 798109 } } ], "vout": [ { "amount": 1391661795, "target": { "key": "a1c77cd01c9951f42de8b9600e0e4c2f37df21484544c7f2d493a021a49f4074" } } ], "extra": [ 1, 23, 87, 252, 95, 243, 91, 69, 98, 222, 138, 25, 106, 209, 165, 118, 65, 90, 61, 179, 222, 128, 176, 15, 47, 192, 232, 130, 125, 208, 150, 0, 81, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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