Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85737a04d5ebcc0e89c5298bc6abdf7aae27ae531c3df39ab6a90cc6b424016e

Tx prefix hash: 5ee254a35b7e9c81f786212f1e7631f1a9f55a1a125f65cb7a0a9bbfad8a6976
Tx public key: d2fe386285d07651ef0c02b85ffec1f8c6143b3aa528f1c0dcc667a11c5df8ae
Timestamp: 1712275128 Timestamp [UCT]: 2024-04-04 23:58:48 Age [y:d:h:m:s]: 01:262:14:26:05
Block: 993497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446418 RingCT/type: yes/0
Extra: 01d2fe386285d07651ef0c02b85ffec1f8c6143b3aa528f1c0dcc667a11c5df8ae02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d0612e2a413112549d51d76a546cca1a2d569452444980022058e0ddeb67876 0.600000000000 1453883 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": 993507, "vin": [ { "gen": { "height": 993497 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d0612e2a413112549d51d76a546cca1a2d569452444980022058e0ddeb67876" } } ], "extra": [ 1, 210, 254, 56, 98, 133, 208, 118, 81, 239, 12, 2, 184, 95, 254, 193, 248, 198, 20, 59, 58, 165, 40, 241, 192, 220, 198, 103, 161, 28, 93, 248, 174, 2, 17, 0, 0, 0, 2, 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