Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26b235d7e25eea5082decce0ee37cd093ca623cbd325a0ffb89694815bf8a5c2

Tx prefix hash: bf153a6173b2f2efd8501c778d9152fe4d2cd5048c50dd6efaa7c4fa7a76076e
Tx public key: 3ee512f74d81fab37b216621f8ec2c69b5c9da86ee8d730cc4e6980b80768686
Timestamp: 1641374454 Timestamp [UCT]: 2022-01-05 09:20:54 Age [y:d:h:m:s]: 02:317:08:58:36
Block: 410798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 745053 RingCT/type: yes/0
Extra: 013ee512f74d81fab37b216621f8ec2c69b5c9da86ee8d730cc4e6980b807686860211000000084a0f5013000000000000000000

1 output(s) for total of 26.721204531000 dcy

stealth address amount amount idx
00: ffa7143122c9d16e9c78bae114d51858e698f6e5ec774fb965b11f90f01b97c8 26.721204531000 813962 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 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": 410808, "vin": [ { "gen": { "height": 410798 } } ], "vout": [ { "amount": 26721204531, "target": { "key": "ffa7143122c9d16e9c78bae114d51858e698f6e5ec774fb965b11f90f01b97c8" } } ], "extra": [ 1, 62, 229, 18, 247, 77, 129, 250, 179, 123, 33, 102, 33, 248, 236, 44, 105, 181, 201, 218, 134, 238, 141, 115, 12, 196, 230, 152, 11, 128, 118, 134, 134, 2, 17, 0, 0, 0, 8, 74, 15, 80, 19, 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