Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 630f71f2347ba757e91d7e5aa891a1fee66793c53192008ab7a83ca323a552a8

Tx prefix hash: 93f921e9d972e9a19f03b7a0f5f6c050832e5489aff4820316c1eac35c991d7a
Tx public key: b844544d5cc3e8d778a412b0bbea84fca44fb132a6840b9776a99659e7d310da
Timestamp: 1707399849 Timestamp [UCT]: 2024-02-08 13:44:09 Age [y:d:h:m:s]: 01:070:08:10:40
Block: 953085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 311343 RingCT/type: yes/0
Extra: 01b844544d5cc3e8d778a412b0bbea84fca44fb132a6840b9776a99659e7d310da02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d10a522e2d822d627d5181e41626513bdd8fb4424d3fffa1a2ff0d5eb2108cea 0.600000000000 1412249 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": 953095, "vin": [ { "gen": { "height": 953085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d10a522e2d822d627d5181e41626513bdd8fb4424d3fffa1a2ff0d5eb2108cea" } } ], "extra": [ 1, 184, 68, 84, 77, 92, 195, 232, 215, 120, 164, 18, 176, 187, 234, 132, 252, 164, 79, 177, 50, 166, 132, 11, 151, 118, 169, 150, 89, 231, 211, 16, 218, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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