Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90c2ff6e913468fd189a0f50217d893c4792c4d33045433e263f6e7448b8eb9c

Tx prefix hash: 420585c7443c838db0320a2757a1bd7dac05231082c16c81e55b60d42678fea9
Tx public key: 042b551f01946c644e2f79e8a95e1576c006cd879f58ba15d93c0f054972fae3
Timestamp: 1724650897 Timestamp [UCT]: 2024-08-26 05:41:37 Age [y:d:h:m:s]: 00:229:15:27:33
Block: 1096106 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163991 RingCT/type: yes/0
Extra: 01042b551f01946c644e2f79e8a95e1576c006cd879f58ba15d93c0f054972fae302110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2206eb4d62d4d6569bd0c8ad0c9dc9e93350a7fd94c2bf78caaa0a8e465e364 0.600000000000 1571293 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 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": 1096116, "vin": [ { "gen": { "height": 1096106 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2206eb4d62d4d6569bd0c8ad0c9dc9e93350a7fd94c2bf78caaa0a8e465e364" } } ], "extra": [ 1, 4, 43, 85, 31, 1, 148, 108, 100, 78, 47, 121, 232, 169, 94, 21, 118, 192, 6, 205, 135, 159, 88, 186, 21, 217, 60, 15, 5, 73, 114, 250, 227, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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