Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8950bf958a6499cc3011a8e4f7c7ead93a5b9c7a0158e49542403768e25b79aa

Tx prefix hash: 4baa30080a49ab28b644314f2729ec3f2615cedb40896e543d9796f042be8c54
Tx public key: b051497560fece572b323a440035afa0e06368cf6a5601041a3f15f3cba9572d
Timestamp: 1739611551 Timestamp [UTC]: 2025-02-15 09:25:51 Age [y:d:h:m:s]: 00:361:19:44:59
Block: 1219669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 256332 RingCT/type: yes/0
Extra: 01b051497560fece572b323a440035afa0e06368cf6a5601041a3f15f3cba9572d021100000004007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8c18e5fa6def9669cc2f5f86b9871dc91510540b5f7bc5a2de610c04fd7579b4 0.000600000000 1706500 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": 1219679, "vin": [ { "gen": { "height": 1219669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c18e5fa6def9669cc2f5f86b9871dc91510540b5f7bc5a2de610c04fd7579b4" } } ], "extra": [ 1, 176, 81, 73, 117, 96, 254, 206, 87, 43, 50, 58, 68, 0, 53, 175, 160, 224, 99, 104, 207, 106, 86, 1, 4, 26, 63, 21, 243, 203, 169, 87, 45, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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) | dinastycoin version: tesla-369