Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c626f64103d565776c0a6e683bd3a44ca340f02a2ff9b8d3ac6b482704553ba0

Tx prefix hash: ab6f251d5fe1065fd87e92b193a970f45fd36ff3501c51ff339025ec787d0daa
Tx public key: 6ce0f891cf15ecf5c2dea3a8a52a0a3b4de5fc9ef7ffb0072a725262f2c2af75
Timestamp: 1635562491 Timestamp [UCT]: 2021-10-30 02:54:51 Age [y:d:h:m:s]: 03:136:04:00:36
Block: 363346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 875604 RingCT/type: yes/0
Extra: 016ce0f891cf15ecf5c2dea3a8a52a0a3b4de5fc9ef7ffb0072a725262f2c2af750211000000164f792ffd000000000000000000

1 output(s) for total of 38.378171031000 dcy

stealth address amount amount idx
00: 0d0e0a1c6af28f208e6ca75dde34e92a1a6fbeac82fbc6ad500490e970169515 38.378171031000 738512 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": 363356, "vin": [ { "gen": { "height": 363346 } } ], "vout": [ { "amount": 38378171031, "target": { "key": "0d0e0a1c6af28f208e6ca75dde34e92a1a6fbeac82fbc6ad500490e970169515" } } ], "extra": [ 1, 108, 224, 248, 145, 207, 21, 236, 245, 194, 222, 163, 168, 165, 42, 10, 59, 77, 229, 252, 158, 247, 255, 176, 7, 42, 114, 82, 98, 242, 194, 175, 117, 2, 17, 0, 0, 0, 22, 79, 121, 47, 253, 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