Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89d8c65ca910dd277be9674cc6d9b8ef70e34fc4c98ec9e6b107adc35bb40aec

Tx prefix hash: 1e971cf31f7cac01f9efbfb5886c77caf249fcd7677388023e6b1f94e82da9ea
Tx public key: 56c365d48a7046de0f5edb984bd6821d32f81c2b8021ef26ec122ac68276d4fd
Timestamp: 1720168830 Timestamp [UCT]: 2024-07-05 08:40:30 Age [y:d:h:m:s]: 00:267:13:52:13
Block: 1058947 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191188 RingCT/type: yes/0
Extra: 0156c365d48a7046de0f5edb984bd6821d32f81c2b8021ef26ec122ac68276d4fd0211000000018fda9b2d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be0bd86860bb46e89cabcf1fea4cd5627b8187f5fd3d8905c45e51df26b88db4 0.600000000000 1529406 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": 1058957, "vin": [ { "gen": { "height": 1058947 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be0bd86860bb46e89cabcf1fea4cd5627b8187f5fd3d8905c45e51df26b88db4" } } ], "extra": [ 1, 86, 195, 101, 212, 138, 112, 70, 222, 15, 94, 219, 152, 75, 214, 130, 29, 50, 248, 28, 43, 128, 33, 239, 38, 236, 18, 42, 198, 130, 118, 212, 253, 2, 17, 0, 0, 0, 1, 143, 218, 155, 45, 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