Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4096c69327ff9632cb8baf9e940c2ffd6ebbe41f47dcde300c74cd0e3ba410c6

Tx prefix hash: c46295620d2af5362b5314939575542005c05d31ef08f805b8ee0d0e0e38394b
Tx public key: 6bf098463e4ad33fc7af7bb6bc7f09d088c88cd1d3a9c9bd12cadf78ea19e896
Timestamp: 1725242872 Timestamp [UCT]: 2024-09-02 02:07:52 Age [y:d:h:m:s]: 00:112:02:15:32
Block: 1101025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80197 RingCT/type: yes/0
Extra: 016bf098463e4ad33fc7af7bb6bc7f09d088c88cd1d3a9c9bd12cadf78ea19e89602110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b8acb65d367ca384cd04030a36883716e6a95319a0f28b93e26b15954dce90a 0.600000000000 1577006 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": 1101035, "vin": [ { "gen": { "height": 1101025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b8acb65d367ca384cd04030a36883716e6a95319a0f28b93e26b15954dce90a" } } ], "extra": [ 1, 107, 240, 152, 70, 62, 74, 211, 63, 199, 175, 123, 182, 188, 127, 9, 208, 136, 200, 140, 209, 211, 169, 201, 189, 18, 202, 223, 120, 234, 25, 232, 150, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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