Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 07cc70726e540ad20d868e8437b1afe0f0bf20505094ff5a6fc3bd1e34db1f87

Tx prefix hash: 2fb486fca64fd112294b36eebcc6d0dbcd6ad38b7eaf6efad0e1e85f5bd2ac7a
Tx public key: 319a3ff8c605b3a88ed484f3ce4176d77a495f00fdc58a908d5c73c38706c1e5
Timestamp: 1770422109 Timestamp [UTC]: 2026-02-06 23:55:09 Age [y:d:h:m:s]: 00:008:07:51:04
Block: 1472270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0908 kB
Tx version: 2 No of confirmations: 5924 RingCT/type: yes/0
Extra: 01319a3ff8c605b3a88ed484f3ce4176d77a495f00fdc58a908d5c73c38706c1e502081c148a1cdb2c2c0b

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 2f62be7146d1acb93ca6e22c527197a04573f29268c1e24b2f431f2c9f1f91f9 0.000600000000 1961548 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": 1472280, "vin": [ { "gen": { "height": 1472270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f62be7146d1acb93ca6e22c527197a04573f29268c1e24b2f431f2c9f1f91f9" } } ], "extra": [ 1, 49, 154, 63, 248, 198, 5, 179, 168, 142, 212, 132, 243, 206, 65, 118, 215, 122, 73, 95, 0, 253, 197, 138, 144, 141, 92, 115, 195, 135, 6, 193, 229, 2, 8, 28, 20, 138, 28, 219, 44, 44, 11 ], "rct_signatures": { "type": 0 } }


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