Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b2786cbff9ffeed7915b418aa06f29f1509018379aefde83a5bebd3d388eb7c

Tx prefix hash: 47753fa8aac92333222c6c3685473f975133fc2772dbad3a2e7e1e961a1434d8
Tx public key: 755960c1e9826359b4bebb99bd458ad67af871dbdc9b867c001c875debf8185b
Timestamp: 1772741862 Timestamp [UTC]: 2026-03-05 20:17:42 Age [y:d:h:m:s]: 00:260:16:43:26
Block: 1491454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191964 RingCT/type: yes/0
Extra: 01755960c1e9826359b4bebb99bd458ad67af871dbdc9b867c001c875debf8185b021100000002f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7c5bc4735b40725e8cc6c99b35bed2e0982274b1fd3cca7b6adc9c79113a11a7 0.000600000000 1980972 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 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": 1491464, "vin": [ { "gen": { "height": 1491454 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c5bc4735b40725e8cc6c99b35bed2e0982274b1fd3cca7b6adc9c79113a11a7" } } ], "extra": [ 1, 117, 89, 96, 193, 233, 130, 99, 89, 180, 190, 187, 153, 189, 69, 138, 214, 122, 248, 113, 219, 220, 155, 134, 124, 0, 28, 135, 93, 235, 248, 24, 91, 2, 17, 0, 0, 0, 2, 241, 136, 200, 168, 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: