Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d261bc3a57e472c317d20dcbd414a5afab7a657c6f7b87280d1d086cd9163fdc

Tx prefix hash: f47c628edc7ba8d251bb5abfa1426cc99a71a844a0d07578ad9fa6edbaa04eae
Tx public key: 95191652a6678473e80881f88a7c17d8fa02a95d488862c3e41b64ac3553408f
Timestamp: 1713170887 Timestamp [UCT]: 2024-04-15 08:48:07 Age [y:d:h:m:s]: 01:199:04:22:40
Block: 1000930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 401016 RingCT/type: yes/0
Extra: 0195191652a6678473e80881f88a7c17d8fa02a95d488862c3e41b64ac3553408f02110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a022d4d7671d07f50671613e8ee671e92ae2286d7d81e35a660fddf0fde2affc 0.600000000000 1461430 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": 1000940, "vin": [ { "gen": { "height": 1000930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a022d4d7671d07f50671613e8ee671e92ae2286d7d81e35a660fddf0fde2affc" } } ], "extra": [ 1, 149, 25, 22, 82, 166, 103, 132, 115, 232, 8, 129, 248, 138, 124, 23, 216, 250, 2, 169, 93, 72, 136, 98, 195, 228, 27, 100, 172, 53, 83, 64, 143, 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