Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7edd1017995aa53294c17b703660892a980a6bb9989dc1508c05554bf2e945c9

Tx prefix hash: 2f1c13bc0cb5d238f4a15f950dd6821dcb125cd363cb2dab183f00f92b80ec54
Tx public key: e89f3e37b9819a11834e18a9fee61068c98d58563fb793e52d38d44f63081ad2
Timestamp: 1735526440 Timestamp [UCT]: 2024-12-30 02:40:40 Age [y:d:h:m:s]: 00:311:10:04:55
Block: 1186142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220064 RingCT/type: yes/0
Extra: 01e89f3e37b9819a11834e18a9fee61068c98d58563fb793e52d38d44f63081ad20211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cd52ba11c1581721ccf1883f3f10a85f5c07c87e8fefa09574442458630f719 0.600000000000 1672621 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": 1186152, "vin": [ { "gen": { "height": 1186142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cd52ba11c1581721ccf1883f3f10a85f5c07c87e8fefa09574442458630f719" } } ], "extra": [ 1, 232, 159, 62, 55, 185, 129, 154, 17, 131, 78, 24, 169, 254, 230, 16, 104, 201, 141, 88, 86, 63, 183, 147, 229, 45, 56, 212, 79, 99, 8, 26, 210, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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