Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fb5edad14404031acdf359aad6bedea45a62786d3a58b5d43b10c2f69eac7e44

Tx prefix hash: c236c5ff1ae1f7c4c95ef092745e8e519dbb1e0ded3e028b3e4be23487babc4f
Tx public key: a0ebe66da8b2c96eb34fdadc7c904fafe2333dc968be5f59154edc39ba3e803f
Timestamp: 1661387425 Timestamp [UCT]: 2022-08-25 00:30:25 Age [y:d:h:m:s]: 02:221:02:34:54
Block: 573149 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 679248 RingCT/type: yes/0
Extra: 01a0ebe66da8b2c96eb34fdadc7c904fafe2333dc968be5f59154edc39ba3e803f021100000002faf35c9c000000000000000000

1 output(s) for total of 7.743183223000 dcy

stealth address amount amount idx
00: f1548b9f805b0d3b308bceb5e85f8ce3ea461efdb19fc78a90d3a9585708d6d1 7.743183223000 1006425 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": 573159, "vin": [ { "gen": { "height": 573149 } } ], "vout": [ { "amount": 7743183223, "target": { "key": "f1548b9f805b0d3b308bceb5e85f8ce3ea461efdb19fc78a90d3a9585708d6d1" } } ], "extra": [ 1, 160, 235, 230, 109, 168, 178, 201, 110, 179, 79, 218, 220, 124, 144, 79, 175, 226, 51, 61, 201, 104, 190, 95, 89, 21, 78, 220, 57, 186, 62, 128, 63, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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