Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb460cd497750c52ddce445077e60d53b903cee8bab8413f8cd78263fe10fc56

Tx prefix hash: 8ddabd22d0caf5cee5aa105fe942cc94e690a8397ea2999916bb6cf6dd52a457
Tx public key: b08b0a8c30d8ff44aafb3be525207dcc9b73d9edc42a925df157e9146d1a0795
Timestamp: 1657095459 Timestamp [UTC]: 2022-07-06 08:17:39 Age [y:d:h:m:s]: 04:137:13:26:46
Block: 537746 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1144437 RingCT/type: yes/0
Extra: 01b08b0a8c30d8ff44aafb3be525207dcc9b73d9edc42a925df157e9146d1a0795021100000004faf35c9c000000000000000000

1 output(s) for total of 0.010144354635 xmr

stealth address amount amount idx tag
00: 1ea10da14a7dacea4c4cdae6443f7c895fecfcaccc656e97e9fd8bde4f3f1398 0.010144354635 967661 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 dinastycoin-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": 537756, "vin": [ { "gen": { "height": 537746 } } ], "vout": [ { "amount": 10144354635, "target": { "key": "1ea10da14a7dacea4c4cdae6443f7c895fecfcaccc656e97e9fd8bde4f3f1398" } } ], "extra": [ 1, 176, 139, 10, 140, 48, 216, 255, 68, 170, 251, 59, 229, 37, 32, 125, 204, 155, 115, 217, 237, 196, 42, 146, 93, 241, 87, 233, 20, 109, 26, 7, 149, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: