Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 33c517d16b5548e18a9400b064b58e1845b963e994fba5fbeef98b7fa264375f

Tx prefix hash: 98a1e1f1bd8a26a6fc45aeef5b0608ad975d404c89c3d37bbc5f4f884cee1cd3
Tx public key: da034ee9bff8cfc5034c58e88670f0cc5deb3a2b20d6f6626e36a59247068e82
Timestamp: 1578592440 Timestamp [UCT]: 2020-01-09 17:54:00 Age [y:d:h:m:s]: 04:361:07:28:49
Block: 42009 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1147682 RingCT/type: yes/0
Extra: 01da034ee9bff8cfc5034c58e88670f0cc5deb3a2b20d6f6626e36a59247068e820211000000124943cd9f000000000000000000

1 output(s) for total of 445.458847304000 dcy

stealth address amount amount idx
00: a6bf449be112c396626ae1c0c79f9115a411cb977ab48f0db85a43dbb0610d9a 445.458847304000 75493 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": 42019, "vin": [ { "gen": { "height": 42009 } } ], "vout": [ { "amount": 445458847304, "target": { "key": "a6bf449be112c396626ae1c0c79f9115a411cb977ab48f0db85a43dbb0610d9a" } } ], "extra": [ 1, 218, 3, 78, 233, 191, 248, 207, 197, 3, 76, 88, 232, 134, 112, 240, 204, 93, 235, 58, 43, 32, 214, 246, 98, 110, 54, 165, 146, 71, 6, 142, 130, 2, 17, 0, 0, 0, 18, 73, 67, 205, 159, 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